home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
dirut
/
sst_53a.zip
/
HISTORY.DOC
< prev
next >
Wrap
Text File
|
1991-07-02
|
17KB
|
324 lines
SST: the Supersonic Search Tool
History of Changes
-------------------------------
v5.3a o Added support for "ARJ" archives. ARJ has taken the
place of "PAK" files internally in SST. However,
.PAK files are still searched if you are doing
archive searching -- you just won't find PAK files
referenced anywhere on SST's menus or command line
switches.
v5.2b o Fixed a bug where the "&d" replaceable parameter was
retaining the trailing '\' if the &d was the last
thing on the command line.
o Added support for EGA/VGA 43/50 line screen displays.
This feature is automatic; no switches are needed.
v5.2a o SST's "archive searching" is now compatible with the
new version of LHARC (v2.10). SST also retains its
compatibility with earlier LHARC archive files.
o Added a new "-ho" switch which tells SST to (a) start
in the current directory, and (b) to ONLY search this
directory (ie: don't search directories under this
directory). This means that SST can now be used as a
true "directory alias" that also lists archive members.
Just create this ARCDIR.BAT file:
sst %1 -ho -a
o Modified the -c"command" switch so that you can now
tell SST to get verification from you. This is done
with the -cv"command" switch. Before executing the
command on each found file, SST will prompt you as to
whether it should execute the command or not.
o In the -c"command" and -v"command" switches you can now
place an ampersand (&) as part of the command string by
entering two ampersands in a row (&&), as in:
-c"echo This && That"
which will now be parsed down to "This & That".
o Fixed a minor bug that would allow you to enter a null
grep string (eg: SST ""), which would of course drive
the regular-expression code completely batty.
v5.1a o After many painstaking hours of debugging, I finally
found the two obscure bugs that were causing random
lockups of the code for some people (since v4.1a of
the program - this will teach me to not use function
prototypes!). I'd like to thank all of you people
who took the time to both call and write with very
good examples of your configurations and problems.
Hopefully, we've put this baby to bed once and for
all. By the way, the Turbo C v1.01 compiler was not
the problem -- this one was all on my shoulders
(my apologies, Borland ... I should have known better!).
o Per a user's request, added a new replaceable parameter
named "&r" that only returns the "root" of the filename
(eg: the filename without the extension).
o SST v5.1a is now compiled with Borland C++ v2.0.
v5.0a o Changed the name of the program from WHEREIS to
SST ("Supersonic Search Tool"). The main reason
behind this was the literally hundreds of requests
I've had over the last few months to give the program
a unique name. To quote a few hundred people:
"There must be a thousand 'Whereis' programs out
there! I'm sooooo confused!". (Well, maybe they
weren't THAT forlorned <grin>. Anyway, from now on
the program will be known as SST_vvv.ZIP on all
BBS's, where "_vvv" will be the version number (as
in SST_50A.ZIP for version 5.0a).
Of course, if you prefer to keep it named WHEREIS
after you download the program, simply rename it and
you'll never know anything changed. For BRANDing
instructions for you registered users, see the
READ.ME file.
o The program will now support the environment variables
SST and SST_DRIVES, as well as the old WHEREIS and
WI_DRIVES. You don't need to change your old ones if
you don't want to.
o The program will no longer prompt you with "You've
asked me do delete ALL FILES on drive x...are you
SURE?" if you specify any exclude masks
(eg: "-x*.bat"). Be careful!
v4.4b o Version 1.03 of PKLite resulted in a header change
in compressed .COM files, which meant that WhereIs
could no longer identify them as compressed files.
This version of WhereIs can now identify those
files.
v4.4a o WhereIs now has the ability to search for COM and
EXE files that have been compressed with PK-Ware's
new PKLite program. Since only .EXE and .COM files
will be "included" if you specify the "-PKLITE"
switch, you can greatly speed up the search time by
doing a command line like this:
WhereIs *.com *.exe -pklite
You can still do all commands on found files; so, for
example, you could un-pklite all PKLite'd files on
your drive with the following command:
WhereIs *.com -pklite -c"pklite -x &f"
v4.3a o Evidently, v4.2 of WhereIs brought out a bug in
the Turbo C++ v1.01 compiler. I had a lot of reports
from people about WhereIs "locking up" in strange
ways. One person told me he kept getting "Divide
by zero" errors, and WhereIs doesn't even HAVE a
division statement in it anywhere. Anyway, I
found one situation where I could lock up the
machine every time; when I compiled the exact code
under the old Turbo C 2.0 compiler, it worked just
fine. I barely have time to chase down my own bugs,
let alone Borland's <grin>, so I've went back to
Turbo C 2.0 with v4.3a. If anyone out there has
any more strange lockups happen, PLEASE let me know
(in as detailed a message as possible) what happenned
to you.
o Fixed a bug that was causing regular-expression
searches to not work when looking inside of ZOO
files.
o Added a new "-dir" switch that tells WhereIs to also
look at directory names when matching for filenames.
Any directories found will display as normal, except
the area where the filesize is normally shown will
display "<dir>" instead.
o Added a new '-gf' switch which tells WhereIs to
"go to the directory of the first found file
without prompting me".
o Added a new '&d' replaceable parameter for use
with the '-c' and '-o' command strings. This
will return the same thing as the '&p' (pathname)
parameter, but without the trailing '\' (unless